[core] desc.node: Support the use of custom Python executables for meshroom_compute
#2849
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR updates how the
meshroom_computeexecutable is determined and invoked for each node, allowing for node-specific Python executables instead of using a global default. This provides greater flexibility for nodes that may require different Python environments: for example, in an environment that contains Houdini (which provides its own version of Python), one may want to call "hython" instead "python".A
pythonExecutablemember, set by default to "python", is added to theNodeclass.This is based on #2853, which adds the content of the
binfolder to the packaged version of folder, thus removing the need to distinguish "release mode" from "regular mode".